Displaying payment instrument art

ABSTRACT

Displaying payment instrument art in a proxy card transaction includes a proxy card system that employs a server configured for receiving a plurality of electronic image files for financial payment instruments; receiving information identifying guidelines for determining which of the plurality of electronic image files is appropriate for the corresponding plurality of financial payment instruments; receiving a request to associate a payment instrument with a proxy card account maintained by the one or more computing devices, the request comprising information identifying the payment instrument, the payment instrument being associated with a payment instrument account maintained by a payment instrument system; determining a particular one of the electronic image files associated with the status of the payment instrument account; receiving a verification of the particular one of the electronic image files; and displaying the verified particular one of the electronic image files with the payment instrument on the user computing device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to U.S. Provisional Patent Application No. 61/678,089, filed Jul. 31, 2012 and entitled “Proxy Card System.” The entire disclosure of the above-identified priority application is hereby fully incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to proxy card transactions, and more particularly to a displaying payment instrument art on a user device when conducting a proxy card transaction.

BACKGROUND

In a conventional merchant-consumer financial transaction, the merchant's point of sale terminal or online payment process engine submits a payment request to an acquirer for payment for the transaction. The acquirer then submits the request to authorize the transaction to an issuer through a card network. If funds are available, the issuer sends an authorization code to the acquirer through the card network, and the acquirer notifies the merchant of the approval for the payment transaction. The payment process involves a single payment request generated and submitted by the merchant.

Conventional merchant-consumer financial transactions also have involved payment via a consumer's financial account, such as a debit card, credit card, or stored value card. The consumer card typically accesses only one type of account, which is maintained by only one issuer. For instance, an “issuer1” credit card accesses only the consumer's financial account from “issuer1,” and payment is approved/denied by a single issuer (“issuer1”). Approval or denial of the transaction is dependent upon rules set by the particular issuer, for example, credit limits and geographical limitations. Notification of a violation of these rules results in a declined transaction, and the consumer must contact the issuer to alter the rules or to address a declined transaction.

In a conventional digital wallet application, the user computing device does not display the art associated with the physical payment instrument. The art may be a representation of the face of a physical card that is typically associated with the payment instrument, such as a credit card. Some physical cards have art that varies based on the level of the user. For example, a user that has a higher credit level with a credit card may have a “gold” or “platinum” credit card, and the associated physical card can have art associated with the different levels. Physical loyalty cards can have similar levels of art associated with the user status. Other physical cards can have varying card art.

Additionally or alternatively, some payment instruments can have customizable art for an associated physical card. For example, a user can choose from a selection of designs, pictures, or other suitable art. In another example, a user can submit a picture or design to be printed on the physical card.

Conventional digital wallet applications do not allow the payment instrument art to be displayed on a user device when using a proxy card account.

SUMMARY

One aspect of the example embodiments described herein provides a computer-implemented method to display payment instrument art on a user device in a proxy transaction. A payment system employs a server configured for receiving, using one or more computing devices, a plurality of electronic image files for a plurality of art available for a corresponding plurality of financial payment instruments; receiving information identifying guidelines for determining which of the plurality of electronic image files is appropriate for the corresponding plurality of financial payment instruments; receiving a request to associate a payment instrument with a proxy card account maintained by the one or more computing devices, the request comprising information identifying the payment instrument, the payment instrument being associated with a payment instrument account maintained by a payment instrument system; identifying a status of the payment instrument account on the payment instrument system; determining a particular one of the electronic image files associated with the status of the payment instrument account, the particular one of the electronic image files being determined based at least in part on the guidelines; receiving a verification of the particular one of the electronic image files; and displaying the verified particular one of the electronic image files with the payment instrument on the user computing device, the displaying step being performed at the time of a transaction using the payment instrument on the user computing device or upon request input into the user computing device.

Another aspect of the example embodiments described herein provides a computer program product that is installed on a server to display payment instrument art on a user device in a proxy transaction. The computer program product includes a non-transitory computer-readable storage device having computer-readable program instructions stored therein. The computer-readable program instructions include computer program instructions for receiving a plurality of electronic image files for a plurality of art available for a corresponding plurality of financial payment instruments; receiving information identifying guidelines for determining which of the plurality of electronic image files is appropriate for the corresponding plurality of financial payment instruments; receiving a request to associate a payment instrument with a proxy card account maintained by the one or more computing devices, the request comprising information identifying the payment instrument, the payment instrument being associated with a payment instrument account maintained by a payment instrument system; identifying a status of the payment instrument account on the payment instrument system; determining a particular one of the electronic image files associated with the status of the payment instrument account, the particular one of the electronic image files being determined based at least in part on the guidelines; receiving a verification of the particular one of the electronic image files; and displaying the verified particular one of the electronic image files with the payment instrument on the user computing device, the displaying step being performed at the time of a transaction using the payment instrument on the user computing device or upon request input into the user computing device.

These and other aspects, objects, features and advantages of the example embodiments will become apparent to those having ordinary skill in the art upon consideration of the following detailed description of illustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for displaying payment instrument art in a proxy card transaction, in accordance with certain example embodiments.

FIG. 2 is a block flow diagram depicting a method to register a user proxy card and display payment instrument art in a transaction, in accordance with certain example embodiments.

FIG. 3 is a block flow diagram depicting a method for associating art with a payment instrument, in accordance with certain example embodiments.

FIG. 4 is a block flow diagram depicting method for updating the art associated with a payment instrument, in accordance with certain example embodiments.

FIG. 5 is a diagram of a user device displaying payment instrument art associated with a gold card status, in accordance with certain example embodiments.

FIG. 6 is a diagram of a user device displaying payment instrument art associated with a platinum card status, in accordance with certain example embodiments.

FIG. 7 is a block flow diagram depicting a computing machine and a module, in accordance with certain example embodiments.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS Overview

In one example embodiment, proxy card payment systems enable users to utilize a single card to access multiple financial accounts maintained by multiple issuers. The user receives a proxy card from the proxy card system and either creates a new proxy card system account or associates the proxy card with the user's digital wallet account already maintained by the proxy card system.

The user then associates one or more financial card accounts with the proxy account. For example, the user can associate with the user's proxy card account multiple debit/credit cards maintained by multiple issuers (including the proxy card system operating as an issuer), stored value cards (for example, gift cards, prepaid cards, re-loadable transaction cards, exchange cards, and other forms of non-credit based value cards), loyalty cards or store rewards cards, value added service accounts (for example, coupons, vouchers for prepaid offers, redemption offers, and other forms of offers), peer-to-peer transaction accounts, bank accounts and/or other forms of financial card accounts.

The user applies the proxy card to a transaction with the merchant in a manner similar to the application of any financial card to a transaction. The merchant forwards the payment request to the acquirer, which forwards the payment request to the card network. The card network forwards the proxy card payment request to the proxy card system, which functions as the issuer for the payment request. The proxy card system can read proxy card account information from the payment request and can access the user's account associated with the proxy card. If the proxy card system is the issuer of the financial account, the proxy card system will approve or decline the transaction. If another issuer maintains the financial account to be used for the transaction, the proxy card system will generate and send a new payment request to that issuer via the card network.

The proxy card system will receive the authorization message from the issuer via the card network if the transaction is approved. The proxy card system forwards an authorization to the acquirer through the card network, which forwards the authorization to the merchant. The merchant then approves the transaction.

In an example embodiment, other digital wallet accounts that are not financial accounts can be utilized and represented in the digital wallet application module. For example, other digital wallet accounts may comprise an access key, an identification card, a passports, a transit card, a boarding pass, a ticket, a coupon, or any object that can be presented in exchange for goods or services or to gain access to goods or services. Throughout the specification, any reference to a financial account on the digital wallet may refer to any digital wallet account that may be presented in exchange for goods or services or to gain access to goods or services.

In an example embodiment, the art available for a financial payment instrument differs based on the payment instrument system issuing the payment instrument. The art also may differ by one or more programs available for the same payment instrument system. For example, the art available may differ by reward program, the user's level within the reward program, the credit level of the user, the level or program status of the user account, the type of payment instrument offered by the payment instrument system, or the user's personal preference. In an example embodiment, the proxy card system will dynamically present the user with the correct financial payment instrument art. The payment instrument system can provide the proxy card system with an identifier. For example, the identifier can be an issuer identification number range (“IIN”) that designates certain financial payment instruments as corresponding to a payment instrument art image.

In an example embodiment, when the user registers a new financial payment card, the proxy card system determines which payment instrument art image corresponds to the financial payment instrument. In an alternative example embodiment, the user is prompted to select a color or sample payment instrument art image to associate with the financial payment instrument from one or more options when a new payment instrument is registered. In other example embodiments, the user submits art for the display. The user may submit a picture or design to be incorporated on the art for the payment instrument. The proxy card system can incorporate the submitted art in part or in whole with text, logos, or other art required for the instrument art.

When the payment instrument system provides the proxy card system with relevant payment instrument art, the proxy card system can dynamically present the user with the correct payment instrument art in the wallet application. The art can be displayed on the user device while the user is choosing a payment instrument for a proxy card or other transaction before, during, or after the transaction with the merchant. Additionally or alternatively, the art can be displayed to indicate to the user which card is being used for a particular transaction. The card art can be displayed at any other time the associated account is being represented or referenced.

For example, the proxy card system receives payment instrument art for credit cards issued by Bank X. Bank X provides copies of the art and the associated IIN range applicable to each image. The proxy card system maps the card art to the associated IIN ranges and stores it in the data storage unit. When the proxy card system receives registration information from the user for her credit card issued by Bank X, the proxy card system determines the appropriate payment instrument art by cross-referencing the IIN for the user's credit card with the IIN ranges provided by Bank X. Once the proxy card system determines the appropriate payment instrument art, it retrieves the image from the data storage unit and associates the user's credit card with the image. The user's account is updated with the associated payment instrument art so that when the user accesses her digital wallet account online or via her mobile communication device, the payment instrument art image is displayed in connection with her credit card issued by Bank X.

In an example embodiment, the proxy card system can log the status of the user account on the payment instrument system. The proxy card system can recognize if the status of the user has changed to different level. For example, if the user has conducted a number of transactions that exceeds a threshold then the user status may be moved to a higher level, such as moving from “gold” to a “platinum” status. In another example, a user may have achieved enough loyalty points to be promoted to a higher status card.

If the status of the user has changed, the proxy card system can access the appropriate instrument art for the new status. For example, if the user status dropped from a “platinum” level back to a “gold” status, then the proxy card system can change the art associated with the payment instrument to a design associated with the “gold” status.

In certain embodiments, the initial association of the art with the payment instrument and any changes to the art must be approved by the user. If the user does not approve the art and no alternative art is available, then the proxy card system can display a default art for the payment instrument or object type, a generic image for the payment instrument or object type, or may not display any art for the payment instrument or object type.

The functionality of the example embodiments will be explained in more detail in the following description, read in conjunction with the figures illustrating the program flow.

Example System Architectures

Turning now to the drawings, in which like numerals represent like (but not necessarily identical) elements throughout the figures, example embodiments are described in detail.

FIG. 1 is a block diagram depicting a system for displaying payment instrument art in a proxy card transaction, in accordance with certain example embodiments. As depicted in FIG. 1, the system 100 includes network devices 110, 130, 140 and 170 that are configured to communicate with one another via one or more networks 105.

Each network 105 includes a wired or wireless telecommunication means by which network devices (including devices 110, 130, 140 and 170) can exchange data. For example, each network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, a mobile telephone network, or any combination thereof. Throughout the discussion of example embodiments, it should be understood that the terms “data” and “information” are used interchangeably herein to refer to text, images, audio, video, or any other form of information that can exist in a computer-based environment.

Each network device 110, 130, 140 and 170 includes a device having a communication module capable of transmitting and receiving data over the network 105. For example, each network device 110, 130, 140 and 170 can include a server, desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and/or coupled thereto, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device. In the example embodiment depicted in FIG. 1, the network devices 110, 130, 140 and 170 are operated by end-users or consumers, merchant operators, proxy card system operators, and payment instrument system operators, respectively.

The user 101 can use the communication application 112, such as a web browser application or a stand-alone application, to view, download, upload, or otherwise access documents or web pages via a distributed network 105. The network 105 includes a wired or wireless telecommunication system or device by which network devices (including devices 110, 130, 140 and 170) can exchange data. For example, the network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (SAN), personal area network (PAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a virtual private network (VPN), a cellular or other mobile communication network, Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.

The communication application 112 can interact with web servers or other computing devices connected to the network 105, including the point of sale terminal 134 of the merchant system 130, the merchant server 135 of the merchant system 130, and the web server 141 of the proxy card system 140.

The user network device 110 may include a digital wallet application module 111. The digital wallet application module 111 may encompass any application, hardware, software, or process the user device 110 may employ to assist the user 101 in completing a purchase. The digital wallet application module 111 can interact with the communication application 112 or can be embodied as a companion application of the communication application 112. As a companion application, the digital wallet application module 111 executes within the communication application 112. That is, the digital wallet application module 111 may be an application program embedded in the communication application 112.

The user device 110 can include a proxy card application 115. The proxy card application 115 can interact with the communication application 112 or be embodied as a companion application of the communication application 112 and execute within the communication application 112. The proxy card application 115 may further be embodied as a companion application of the digital wallet application module 111 and execute within the digital wallet application module 111. The proxy card application 115 may employ a software interface for configuration that may open in the digital wallet application module 111 or may open in the web browser application 112. Alternatively, the proxy card application 115 may be execute on the user device 110 independent of the digital wallet application module 111 and the communication application 112.

The proxy card application 115 is operable to allow a user 101 to configure a proxy card account on the user device 110 and the proxy card system 140. The proxy card application 115 can allow the user 101 to set rules, choose card art, confirm selections, select preferred cards for a transaction, receive notice of a card selection, and provide other suitable services.

In an example embodiment, the user device 110 also includes a data storage unit 113 accessible by the digital wallet application module 111, the proxy card application 115, and the communication application 112. The example data storage unit 113 can include one or more tangible computer-readable storage devices. The data storage unit 113 can be stored on the user device 110 or can be logically coupled to the user device 110. For example, the data storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory.

In an alternative example embodiment, the user device 110 also includes a web browser that can communicate with the web server 141. The user 101 can interact with the web-based version of the application as rendered by the web server 141.

In an example embodiment, the proxy card looks and/or functions in the same manner as a standard credit or debit card. For example, the proxy card may have the user's 101 name and/or account number listed on the front of the card. An example proxy card can include a magnetic stripe encoding the proxy card system 140 account information of the user 101. In an example embodiment, the account information encoded in the magnetic stripe routes payment requests to the proxy card system 140 for processing.

In an alternative example embodiment, the proxy card is not a physical card. Instead, the proxy card is an account accessible by a wireless tap of a user device 110, an account identification number, a bar code or QR code, a token, or other form of account identification or access, which may be entered manually into the term POS terminal 134 or a terminal reader (not pictured) or which may be captured by the terminal reader. The proxy card as discussed throughout the specification refers to a physical card as well as the proxy account.

The user 101 may use the user device 110 or other network device to register the proxy card and/or access the proxy card system account of the user 101. The user device 110 may comprise appropriate technology that includes or is coupled to a web server (for example, Google Chrome, Microsoft Internet Explorer, Netscape, Safari, Firefox, or other suitable application for interacting with web page files).

The proxy card system 140 includes a data storage unit 147 accessible by the web server 141. The example data storage unit 147 can include one or more tangible computer-readable storage devices.

The user 101 can use the digital wallet application module 111 or a web server 141 on the proxy card system 140 to view, register, download, upload, or otherwise access the proxy card system 140 via a website (not illustrated) and a communication network 105. The user 101 associates one or more registered financial card accounts, including bank account debit cards, credit cards, gift cards, loyalty cards, coupons, offers, prepaid offers, store rewards cards, or other type of financial account that can be used to make a purchase or redeem value-added services with a payment account of the user 101. The proxy card system 140 also may function as the issuer for the associated financial payment instrument. The user's 101 registration information is saved in the proxy card system's 140 data storage unit 147 and is accessible the by web server 141. The user 101 also may use the web server 141 to define payment rules.

The merchant system 130 may use an Internet connected server 135 to view, download, upload, create offers, sell products online, or otherwise access the proxy card system 140 via a website 136 and a communication network 105. The merchant system 130 represents an entity that offers products for the user 101 to purchase or use. The merchant system 130 includes a point of sale (“POS”) terminal 134. The POS terminal 134 may be operated by a salesperson that enters the purchase data into the POS terminal 134 to complete the purchase transaction. The merchant system 130 may be a physical store or an online merchant.

The user 101 may request a purchase from the merchant system 130. In an example embodiment, the purchase is initiated by a wireless “tap” of the mobile device 110 with the POS terminal 134. In an alternative example embodiment, the purchase is initiated when the user 101 enters an account identification number at the POS terminal 134 or in the mobile device 110. In another alternative example embodiment, the purchase is initiated online with the merchant server 135. The purchase may be initiated via the merchant website 136. In yet another alternative example embodiment, the purchase is initiated by use of a permanent/temporary virtual/physical token, magnetic stripe, QR code, bar code, or other suitable machine-readable medium captured by the POS terminal 134. The merchant's POS terminal 134 interacts with an acquirer (for example Chase PaymentTech, or other third party payment processing companies), the card network (for example VISA, MasterCard, American Express, Discover or other card processing networks), the proxy card system 140, and the issuer (for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment).

The payment instrument system 170 represents any the system that issues or maintains a financial account that the can be associated with the proxy card system 140. Examples of the financial accounts that can be associated include, but are not limited to, debit cards, credit cards, stored value cards, loyalty/rewards cards, bank accounts, peer-to-peer transaction accounts, stored value accounts, and coupons (including purchased offers and other offers). The payment instrument system 170 can communicate with the proxy card system 140, the merchant system 130, and the user device 110 as needed to configure accounts, associate payment instruments, supply instrument art, or perform any other suitable functions.

Example Processes

The components of the example operating environment 100 are described hereinafter with reference to the example methods illustrated in FIG. 2.

FIG. 2 is a block flow diagram depicting a method 200 to register a user proxy card and display payment instrument art in a transaction, in accordance with certain example embodiments.

With reference to FIGS. 1 and 2, in block 205, the proxy card system 140 issues a proxy card account to the user 101. In an example embodiment, the user 101 requests a proxy card using a web server 141, and the proxy card is mailed to the user 101. The user 101 may be issued an account number to be used for transactions via the Internet before or after a physical card is received. In an alternative example embodiment, the proxy card system 140 mails an inactivated proxy card to the user 101. The proxy card is then activated by the user 101 before use. In an alternative example embodiment, a physical proxy card is not issued. The proxy card account information can be stored in the user device 110 and is used to make a payment via a NFC, Bluetooth, Wi-Fi, or other form of wireless tap of the user device 110 with the point of sale (“POS”) terminal 134. In an alternative example embodiment, the purchase is initiated when the user 101 enters an account identification number at the POS terminal 134 or in the user device 110. The account identification number may be the proxy card account number or a different number that links the payment transaction to the proxy card account. In yet another alternative example embodiment, a purchase is initiated by use of a permanent/temporary virtual/physical token magnetic stripe, QR code, bar code, or other suitable machine-readable medium that is read by the POS terminal 134. In these cases, the POS terminal 134 may comprise a scanner, camera, credit card terminal, or other reading device that captures the proxy account information, such as a bar code or QR reader, magnetic stripe reader, or other suitable reading device. The proxy account information may be printed in paper or other form.

In block 210, the user 101 creates a new proxy card system 140 account or links the proxy card to an existing account on the proxy card system 140. The proxy card system 140 also may create or update an account on a proxy card application 115 on the user device 110 or on a digital wallet application module 111 on the user device 110.

In block 215, the user 101 activates the proxy card and associates one or more financial instrument accounts (for example, debit cards, credit cards, gift cards/stored value cards, loyalty cards/reward cards, coupons, prepaid or other offers, and other accounts used to make a purchase or redeem value added services) with the proxy card account. In an example embodiment, the user 101 associates multiple financial instrument accounts with the proxy card account. The user 101 may perform this block by inputting identifying information for each financial card account or by allowing the merchant or issuer to push this information into their digital wallet with the user's permission.

In an example embodiment, one or more financial instrument account(s) are maintained by the proxy card system 140 and other payment instrument systems 170. In an alternative example embodiment, the proxy card system 140 maintains one or more of the financial instrument accounts and acts as the issuer for that financial instrument account. In another example embodiment, the financial instrument accounts are maintained by more than one payment instrument systems 170, including the proxy card system 140.

In block 220, the proxy card system 140 determines the appropriate payment instrument art for each payment instrument and associates the art with the payment instruments on the user account. An example method for associating the art with the payment instruments is discussed in greater detail in FIG. 3.

Turning now to FIG. 3, in block 305, the proxy card system 140 accesses payment instrument art guidelines form the payment instrument system 170. The art available for a financial payment instrument differs by payment instrument system 170 issuing the payment instrument. The art also may differ by one or more programs available for the same payment instrument system 170. For example, the art available may differ by reward program, the level of the user 101 within the reward program, the credit level of the user 101, the level or program status of the user account, type of payment instrument offered by the payment instrument system 170, the preference of the user 101, or other suitable program providing art. The payment instrument system 170 provides electronic image files corresponding to the art available for its corresponding payment instruments and levels within each payment instrument. Art displayed by the proxy card system 140 for a particular payment instrument comprises rendering the corresponding electronic image file on the user network device 110.

In an example embodiment, other digital wallet accounts that are not financial accounts can be utilized and represented by the art. For example, other digital wallet accounts may comprise an access key, an identification card, a passports, a transit card, a boarding pass, a ticket, a coupon, or any object that can be presented in exchange for goods or services or to gain access to goods or services. Throughout the specification, any reference to a financial account on the digital wallet may refer to any digital wallet account that may be presented in exchange for goods or services or to gain access to goods or services.

In block 310, the proxy card system 140 presents the user with the recommended financial payment instrument art. In an example embodiment, the payment instrument system 170 will provide the proxy card system 140 with an identifier for the payment instrument. For example, the identifier can be an issuer identification number range (“IIN”) that designates certain financial payment instruments as corresponding to a payment instrument art image. The proxy card system 140 can query the payment instrument system 170 for instrument art associated with the instrument identifier. Any suitable identifier may be employed by the payment instrument system 170. In an alternate embodiment, the payment instrument system 170 can provide a text description of the instrument or any other description or other suitable manner of identifying the payment instrument and the associated art.

The queries and responses between the proxy card system 140 and the payment instrument system 170 can be transmitted via an Internet connection over the network 105, email, text, or other suitable communication technology.

The payment instrument system 170 can maintain one or more payment instrument art choices that can be associated with each payment instrument. The payment instrument may be classified by the type, style, level, or other suitable variation on the payment instrument. Each variation of the payment instrument can be associated with one or more different art choices.

For example, a credit card can have different card art for a user 101 that has attained an elite status than for a user 101 that has opened a new account. In another example, a stored value card may display different art for a card that has a higher balance on the stored value account that for a card that has a lower balance. In another example, a payment instrument can have a similar color or design, but the text can differ. For example, a credit card can display text that identifies the status or level of account achieved by the user 101. A loyalty card can display the loyalty points possessed by the user 101 or a level of loyalty rewards attained. Any other variation in the instrument art can be incorporated to reflect the status of the payment instruments or for any other reason.

If more than one option is available, the user 101 can be prompted to select a payment instrument art image to associate with the financial payment instrument. For example, the payment instrument system 170 may have a selection of card art that has different colors, pictures, or other visual options. Additionally or alternatively, the user 101 can choose from different text options to be displayed on the card art. For example, different words, word groupings, word placements, or fonts may be selected by the user 101.

The options for the art may be presented to the user 101 on the user device 110 via the proxy card application 115, on a website of the payment instrument system 170, a website of the proxy card system 140, or via any other method or means.

In block 315, the proxy card system 140 determines if the payment instrument system 170 allows custom art to be associated with the payment instrument. That is, the payment instrument system 170 may allow the user to submit a picture, design, text, or other features to be substituted or included in the art. If the payment instrument system 170 allows the user 101 to submit customized art to be associated with the payment instrument, then the method 220 follows the “YES” branch of block 315 to block 320. If the payment instrument system 170 does not allow the user 101 to submit customized art to be associated with the payment instrument, then the method 220 follows the “NO” branch of block 315 to block 325.

Following the YES block of block 315 to block 320, the proxy card system 140 receives an input of customized art from the user 101. The user 101 can submit customized art via a website or application on the payment instrument system 170, the proxy card system 140, on the proxy card application 115, or via any other communication device or website. The art can be a drawing, photograph, color preference, text, or any other design that may be totally or partially included in the art associated with the instrument.

In block 325, the proxy card system 140 receives a verification of the selected instrument art from the user 101. Based on the input of the user 101, the options presented by the payment instrument system 170, or other input, the proxy card system 140 can provide to the user 101 a representation of how the instrument will appear when used in a proxy card transaction. The representation can be presented on a website on the payment instrument system 170, the proxy card system 140, on the proxy card application 115 or via any other communication device or website. The user 101 can confirm that the representation is acceptable to the user 101. If the user does not approve of the representation, some or all of the selection process of blocks 305 to 320 can be repeated to produce a new instrument art presentation. Alternatively, the proxy card system 140 can employ a default instrument art or no art at all if the user 101 does not approve the selection.

From block 325, the method 220 returns to block 225 of FIG. 2.

In block 225, the proxy card system 140 associates the selected and verified art with the payment instrument. The proxy card system 140 stores the instrument art on the server 141 for display on the user device 110 and a proxy card system website. Additionally or alternatively, the instrument art is transmitted to the user device 110 for storage on the data storage unit 113. The instrument art can be stored on any other suitable computing system for display to a user 101 or others.

In block 230, the proxy card system 140 sends the user proxy card account identification information to the card network (not shown). The POS terminal 134 can identify the account number as belonging to a proxy card account on the proxy card system 140. Alternatively, the identification of the proxy card and the proxy card system 140 can occur at any place in the system of merchant system 130, acquirer, card network, or payment instrument system 170.

In block 235, the card network stores the proxy card account identification information. In an alternative example embodiment, the account number identifies the proxy card system 140 as the issuer and payments are automatically routed from the card network to the proxy card system 140 for approval.

In alternate embodiments, the proxy card account can be configured through any other process. For example, the proxy card may be hidden from the user 101. The user 101 may configure an account with the proxy card system 140 and have a proxy card automatically installed on the account for use with the user device 110 or other device. The account may be linked to a financial account or other account of the user 101. The user 101 may choose one financial account to be the active account and the selected financial account can become the backing instrument for the proxy card.

In another example, the method 200 can perform block 210 after blocks 220 and 230 are performed. That is, the user 101 can create a proxy card system 140 account and associate one or more financial accounts with the proxy card system 140 account. The proxy card system 140 may then issue a proxy card and associate the proxy card with the account of the user 101.

In block 240, the proxy card is used to conduct a transaction with a merchant system 130. The merchant system 130 can be at a physical merchant location or an online merchant location. The user 101 can select one or more products for purchase and initiate a transaction with the proxy card. As previously described, the initiation can be via a physical proxy card, contactless transaction with a user device, or an online transaction.

In block 245, the proxy card application 115 on a user device 110 can display to the user 101 the payment instrument that is selected to conduct the transaction. The selection by the proxy card application 115 can be based on rules established by the user 101 during configuration. For example, the proxy card rules can select a payment instrument based on the location of the user device 110, the type of merchant system 130, the balance on the payment instruments, or any other suitable rules established by the user 101 and the proxy card system 140. In another example, a payment instrument can be designated as the default card for all transactions that are not otherwise associated with a rule.

In an alternate example embodiment, the proxy card application 115 displays some or all of the payment instruments associated with the proxy card account of the user 101 for selection by the user 101. The proxy card application 115 can display the art for each of the payment instruments to assist the user 101 in making the selection.

In block 250, the user 101 selects the payment instrument for use in the transaction. The user 101 can make a selection by actuating a physical or virtual button, by a voice command, by tapping the appropriate representation of the payment instrument, or by any other suitable manner of selecting an instrument. After a selection is made by the user 101, the selected payment instrument and the associated art can be displayed on the user device 110.

In an alternate example embodiment the blocks 240, 245, and block 250 can be conducted in any order. For example, the user 101 can select a payment instrument before initiating a transaction. In another example, the user 101 selects the payment instrument from a list and the associated art is not displayed until after a selection is made. The steps can be conducted in any other suitable order.

In an alternate example embodiment, the proxy card system 115 can conduct the transaction without the selection of a payment instrument. At a time after the transaction is conducted, or at any time during the transaction, the payment instrument can be selected. The selection can be based on a set of rules as described above or can be made by the user 101 of the proxy card system 140.

FIG. 4 is a block flow diagram depicting method for updating the art associated with a payment instrument, in accordance with certain example embodiments.

In block 405, the proxy card system 140 logs the status of the user account. The proxy card system 140 can obtain the transaction history of the user 101 by logging the associated proxy card transactions, from the payment instrument system 170, from the card network, or from any other source. The proxy card system 140 can obtain the transaction history of the user 101 from the payment instrument system 170 periodically or the proxy card system 140 can obtain information on each transaction of the user 101 at the time of each transaction. The proxy card system 140 can query the payment instrument system 170 for the status or transaction history of the user 101. In any other suitable manner, the proxy card system 140 can obtain the user status.

In block 410, the proxy card system 140 compares the transaction history with the guidelines of the payment instrument system 170 to determine the status of the user 101. The proxy card system 140 can use the determined or provided status to determine the appropriate card art to be associated with the account. Thus, when the status of a user 101 changes, the proxy card system 140 can determine if the art is appropriate to the new status. In another example embodiment, the proxy card system 140 can query the payment instrument system 170 to receive updates of the status of the user 101. The status can be provided by the payment instrument system 170 in any suitable form. In an example, the payment instrument system 170 can provide the issuer identification number of the account. In another example, the payment instrument system 170 can provide a description of other text describing the status of the user 101. In another example, the payment instrument system 170 can directly provide the art appropriate for the status of the user 101. The proxy card system 140 can recognize if the status of the user 101 has changed to different level.

The status of a user 101 can change for any suitable reason, such as earning a level change in a point or reward based system, a credit rating change, a change in the payment instrument system 170 guidelines, a request by the user 101, or any other suitable reason. For example, if the user 101 has conducted a number of transactions that exceeds a threshold then the user status may be moved to a higher level, such as moving from “silver” to a “gold” card status. In another example, a user 101 may have achieved enough loyalty points to be promoted to a higher status card. In an example embodiment, the proxy card system 140 receives the status level information from the payment instrument system 170, the proxy card system 140 can monitor the user's 101 transactions and can compare those transactions to the status level information to determine the appropriate status for which the user 101 qualifies. In an alternative example embodiment, the payment instrument system 170 can communicate the new status level information for the user 101 to the proxy card system 140.

In block 415, if the status of the payment instrument of the user 101 has changed, then the method 400 can follow the “YES” branch of block 415 to block 220. If the status of the payment instrument of the user 101 has not changed, then the method 400 can follow the “NO” branch of block 415 to block 405.

Following the NO branch of block 415, the method 400 returns to block 405 and continues to monitor the status of the user account.

Following the YES branch of block 415 to block 220, the proxy card system 140 determines appropriate payment instrument art and associates art with each payment instrument. The details of block 220 are described in greater detail in block 220 of FIG. 2 and method 220 of FIG. 3.

In block 420, the proxy card system 140 associates the selected and verified art with the payment instrument. The proxy card system 140 stores the instrument art on the server 141 for display on the user device 110 and a proxy card system website. Additionally or alternatively, the instrument art is transmitted to the user device 110 for storage on the data storage unit 113. The instrument art can be stored on any other suitable computing system for display to a user 101 or others.

The proxy card system 140 can access the appropriate instrument art for the new status. For example, if the user status dropped from a “platinum” level back to a “silver” status, then the proxy card system 140 can change the art associated with the payment instrument to a design associated with the “silver” status. In another example, the art may change based on the level of funds available on a stored value card or credit available on a credit card. That is, the color of the card may change as more or less funds are available, such as turning red as funds available diminish. In another example, a display of funds available may change, such as a graph showing available funds changing as funds are added or depleted. Any other suitable indicator of the user status may be displayed in the art.

FIG. 5 is a diagram of a user device 110 displaying payment instrument art associated with a “Gold” card status, in accordance with certain example embodiments. In an example embodiment, the user device 110 is a mobile phone with a display for a user interface. The user interface displays a digital wallet application module 111 allowing a selection of a payment instrument for a transaction. In the example, the payment instrument is a credit card issued by ABC Bank. The credit card account of the user 101 at the ABC Bank is at a status level of Gold. The display on the user device 110 shows the payment instrument art associated with the Gold level of credit card.

FIG. 6 is a diagram of a user device 110 displaying payment instrument art associated with a “Platinum” card status. In an example embodiment, the status of the credit card issued by ABC Bank that is associated with a user 101 has been upgraded from Gold level to a Platinum level. The payment instrument art associated with the credit card has been updated to art associated with the Platinum status. When the user 101 accesses the payment instruments in the digital wallet application module 111, the Platinum payment instrument art is displayed.

Example Systems

FIG. 7 depicts a computing machine 2000 and a module 2050 in accordance with certain example embodiments. The computing machine 2000 may correspond to any of the various computers, servers, mobile devices, embedded systems, or computing systems presented herein. The module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 in performing the various methods and processing functions presented herein. The computing machine 2000 may include various internal or attached components such as a processor 2010, system bus 2020, system memory 2030, storage media 2040, input/output interface 2060, and a network interface 2070 for communicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computer system, an embedded controller, a laptop, a server, a mobile device, a smartphone, a set-top box, a kiosk, a vehicular information system, one more processors associated with a television, a customized machine, any other hardware platform, or any combination or multiplicity thereof. The computing machine 2000 may be a distributed system configured to function using multiple computing machines interconnected via a data network or bus system.

The processor 2010 may be configured to execute code or instructions to perform the operations and functionality described herein, manage request flow and address mappings, and to perform calculations and generate commands. The processor 2010 may be configured to monitor and control the operation of the components in the computing machine 2000. The processor 2010 may be a general purpose processor, a processor core, a multiprocessor, a reconfigurable processor, a microcontroller, a digital signal processor (“DSP”), an application specific integrated circuit (“ASIC”), a graphics processing unit (“GPU”), a field programmable gate array (“FPGA”), a programmable logic device (“PLD”), a controller, a state machine, gated logic, discrete hardware components, any other processing unit, or any combination or multiplicity thereof. The processor 2010 may be a single processing unit, multiple processing units, a single processing core, multiple processing cores, special purpose processing cores, co-processors, or any combination thereof. According to certain embodiments, the processor 2010 along with other components of the computing machine 2000 may be a virtualized computing machine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such as read-only memory (“ROM”), programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), flash memory, or any other device capable of storing program instructions or data with or without applied power. The system memory 2030 may also include volatile memories such as random access memory (“RAM”), static random access memory (“SRAM”), dynamic random access memory (“DRAM”), synchronous dynamic random access memory (“SDRAM”). Other types of RAM also may be used to implement the system memory 2030. The system memory 2030 may be implemented using a single memory module or multiple memory modules. While the system memory 2030 is depicted as being part of the computing machine 2000, one skilled in the art will recognize that the system memory 2030 may be separate from the computing machine 2000 without departing from the scope of the subject technology. It should also be appreciated that the system memory 2030 may include, or operate in conjunction with, a non-volatile storage device such as the storage media 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compact disc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), a Blu-ray disc, a magnetic tape, a flash memory, other non-volatile memory device, a solid sate drive (“SSD”), any magnetic storage device, any optical storage device, any electrical storage device, any semiconductor storage device, any physical-based storage device, any other data storage device, or any combination or multiplicity thereof. The storage media 2040 may store one or more operating systems, application programs and program modules such as module 2050, data, or any other information. The storage media 2040 may be part of, or connected to, the computing machine 2000. The storage media 2040 may also be part of one or more other computing machines that are in communication with the computing machine 2000 such as servers, database servers, cloud storage, network attached storage, and so forth.

The module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 with performing the various methods and processing functions presented herein. The module 2050 may include one or more sequences of instructions stored as software or firmware in association with the system memory 2030, the storage media 2040, or both. The storage media 2040 may therefore represent examples of machine or computer readable media on which instructions or code may be stored for execution by the processor 2010. Machine or computer readable media may generally refer to any medium or media used to provide instructions to the processor 2010. Such machine or computer readable media associated with the module 2050 may comprise a computer software product. It should be appreciated that a computer software product comprising the module 2050 may also be associated with one or more processes or methods for delivering the module 2050 to the computing machine 2000 via the network 2080, any signal-bearing medium, or any other communication or delivery technology. The module 2050 may also comprise hardware circuits or information for configuring hardware circuits such as microcode or configuration information for an FPGA or other PLD.

The input/output (“I/O”) interface 2060 may be configured to couple to one or more external devices, to receive data from the one or more external devices, and to send data to the one or more external devices. Such external devices along with the various internal devices may also be known as peripheral devices. The I/O interface 2060 may include both electrical and physical connections for operably coupling the various peripheral devices to the computing machine 2000 or the processor 2010. The I/O interface 2060 may be configured to communicate data, addresses, and control signals between the peripheral devices, the computing machine 2000, or the processor 2010. The I/O interface 2060 may be configured to implement any standard interface, such as small computer system interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel, peripheral component interconnect (“PCI”), PCI express (PCIe), serial bus, parallel bus, advanced technology attached (“ATA”), serial ATA (“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, various video buses, and the like. The I/O interface 2060 may be configured to implement only one interface or bus technology. Alternatively, the I/O interface 2060 may be configured to implement multiple interfaces or bus technologies. The I/O interface 2060 may be configured as part of, all of, or to operate in conjunction with, the system bus 2020. The I/O interface 2060 may include one or more buffers for buffering transmissions between one or more external devices, internal devices, the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to various input devices including mice, touch-screens, scanners, biometric readers, electronic digitizers, sensors, receivers, touchpads, trackballs, cameras, microphones, keyboards, any other pointing devices, or any combinations thereof. The I/O interface 2060 may couple the computing machine 2000 to various output devices including video displays, speakers, printers, projectors, tactile feedback devices, automation control, robotic components, actuators, motors, fans, solenoids, valves, pumps, transmitters, signal emitters, lights, and so forth.

The computing machine 2000 may operate in a networked environment using logical connections through the network interface 2070 to one or more other systems or computing machines across the network 2080. The network 2080 may include wide area networks (WAN), local area networks (LAN), intranets, the Internet, wireless access networks, wired networks, mobile networks, telephone networks, optical networks, or combinations thereof. The network 2080 may be packet switched, circuit switched, of any topology, and may use any communication protocol. Communication links within the network 2080 may involve various digital or an analog communication media such as fiber optic cables, free-space optics, waveguides, electrical conductors, wireless links, antennas, radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of the computing machine 2000 or the various peripherals discussed herein through the system bus 2020. It should be appreciated that the system bus 2020 may be within the processor 2010, outside the processor 2010, or both. According to some embodiments, any of the processor 2010, the other elements of the computing machine 2000, or the various peripherals discussed herein may be integrated into a single device such as a system on chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personal information about users, or may make use of personal information, the users may be provided with a opportunity to control whether programs or features collect user information (e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location), or to control whether and/or how to receive content from the content server that may be more relevant to the user. In addition, certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, ZIP code, or state level), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about the user and used by a content server.

Embodiments may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions. However, it should be apparent that there could be many different ways of implementing embodiments in computer programming, and the embodiments should not be construed as limited to any one set of computer program instructions. Further, a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed embodiments based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use embodiments. Further, those skilled in the art will appreciate that one or more aspects of embodiments described herein may be performed by hardware, software, or a combination thereof, as may be embodied in one or more computing systems. Moreover, any reference to an act being performed by a computer should not be construed as being performed by a single computer as more than one computer may perform the act.

The example embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described previously. The systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry. The software can be stored on computer-readable media. For example, computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc. Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodiments presented previously are illustrative, and, in alternative embodiments, certain acts can be performed in a different order, in parallel with one another, omitted entirely, and/or combined between different example embodiments, and/or certain additional acts can be performed, without departing from the scope and spirit of various embodiments. Accordingly, such alternative embodiments are included in the inventions described herein.

Although specific embodiments have been described above in detail, the description is merely for purposes of illustration. It should be appreciated, therefore, that many aspects described above are not intended as required or essential elements unless explicitly stated otherwise. Modifications of, and equivalent components or acts corresponding to, the disclosed aspects of the example embodiments, in addition to those described above, can be made by a person of ordinary skill in the art, having the benefit of the present disclosure, without departing from the spirit and scope of embodiments defined in the following claims, the scope of which is to be accorded the broadest interpretation so as to encompass such modifications and equivalent structures. 

What is claimed is:
 1. A computer-implemented method to display payment instrument art on user computing devices, comprising: receiving, using one or more computing devices, a plurality of electronic image files for a plurality of art available for a corresponding plurality of financial payment instruments; receiving, using the one or more computing devices, guidelines for determining which of the plurality of electronic image files is appropriate for the corresponding plurality of financial payment instruments; receiving, using the one or more computing devices, a request to associate a payment instrument with a proxy card account maintained by the one or more computing devices, the request comprising information identifying the payment instrument, the payment instrument being associated with a payment instrument account maintained by a payment instrument system; identifying, using the one or more computing devices, a status of the payment instrument account on the payment instrument system; determining, using the one or more computing devices, a particular one of the electronic image files associated with the status of the payment instrument account, the particular one of the electronic image files being determined based at least in part on the guidelines; receiving, using the one or more computing devices and from a user computing device, a verification of the particular one of the electronic image files; and displaying, using the one or more computing devices, the verified particular one of the electronic image files with the payment instrument on the user computing device, the displaying step being performed at the time of a transaction using the payment instrument on the user computing device or upon request input into the user computing device.
 2. The computer-implemented method of claim 1, further comprising: displaying, using the one or more computing devices, one or more options for the particular one of the electronic image files for selection on the user computing device; and receiving, using the one or more computing devices and from the user computing device, a selection of the particular one of the electronic image files to be associated with the payment instrument.
 3. The computer-implemented method of claim 2, further comprising: receiving, using the one or more computing devices, electronic art input into the user computing device, the submitted electronic art complying with the guidelines; and incorporating, using the one or more computing devices, the submitted art into the options.
 4. The computer-implemented method of claim 2, further comprising: determining, using the one or more computing devices, that the payment instrument account has encountered a change of status; determining, using the one or more computing devices, if the status of the payment instrument account requires a new electronic image file based at least in part on the guidelines and the change of status; and updating, using the one or more computing devices, the particular one of the electronic image files associated with the payment instrument based on the guidelines and the change of status.
 5. The computer-implemented method of claim 1, the information identifying the payment instrument comprising an issuer identification number.
 6. The computer-implemented method of claim 1, the payment instrument comprising a credit card, a debit card, a stored value card, a loyalty card, a peer-to-peer transaction account, a value added service account, or a bank account.
 7. The computer-implemented method of claim 1, each of the electronic image files comprising a virtual representation of a physical card associated with the payment instrument.
 8. The computer-implemented method of claim 7, the virtual representation comprising a color of the card, a picture on the card, or a set of written text on the card.
 9. A computer program product, comprising: a non-transitory computer-readable storage device having computer-readable program instructions embodied thereon that when executed by a computer perform a method to display digital wallet object art on user computing devices, the computer-readable program instructions comprising: computer program instructions to receive a plurality of electronic image files for a plurality of art available for a corresponding plurality of digital wallet objects; computer program instructions to receive guidelines for determining which of the plurality of electronic image files is appropriate for the corresponding plurality of digital wallet objects; and computer program instructions to receive a request to associate a digital wallet object with an account maintained by the one or more computing devices, the request comprising information identifying the digital wallet object, the digital wallet object being associated with a digital wallet account maintained by an issuer of the digital wallet object; computer program instructions to determine a particular one of the electronic image files associated with the status of the digital wallet account, the particular one of the electronic image files being determined based at least in part on the guidelines; and computer program instructions to display the determined particular one of the electronic image files with the digital wallet object on the user computing device.
 10. The computer program product of claim 9, further comprising: computer-executable program instructions to receive, from a user computing device, a verification of the particular one of the electronic image files; and computer program instructions to display the verified particular one of the electronic image files with the digital wallet object on the user computing device.
 11. The computer program product of claim 9, wherein the displaying step is performed at the time of a transaction using the digital wallet object on the user computing device or upon request input into the user computing device.
 12. The computer program product of claim 9, further comprising computer-executable program instructions to identify a status of the digital wallet object account on the issuer of the digital wallet object.
 13. The computer program product of claim 9, the digital wallet object comprising a credit card, a debit card, a stored value card, a loyalty card, a peer-to-peer transaction account, a value added service account, or a bank account or other digital wallet account comprising an access key, an identification card, a passport, a transit card, a boarding pass, a ticket, a coupon, or any object that can be presented in exchange for goods or services or to gain access to goods or services.
 14. The computer program product of claim 9, further comprising: computer-executable program instructions to display one or more options for the particular one of the electronic image files for selection on the user computing device; and computer-executable program instructions to receive from the user computing device, a selection of the particular one of the electronic image files to be associated with the digital wallet object.
 15. The computer program product of claim 9, further comprising: computer-executable program instructions to receive electronic art input into the user computing device, the submitted electronic art complying with the guidelines; and computer-executable program instructions to incorporate the submitted art into the options.
 16. A system to use a one-time code to display payment instrument art on user computing devices, the system comprising: a storage resource; a network module; and a processor communicatively coupled to the storage resource and the network module, wherein the processor executes application code instructions that are stored in the storage resource and that cause the system to: receive a plurality of electronic image files for a plurality of art available for a corresponding plurality of financial payment instruments; receive guidelines for determining which of the plurality of electronic image files is appropriate for the corresponding plurality of financial payment instruments; receive a request to associate a payment instrument with a proxy card account maintained by the one or more computing devices, the request comprising information identifying the payment instrument, the payment instrument being associated with a payment instrument account maintained by a payment instrument system; determine a particular one of the electronic image files associated with the status of the payment instrument account, the particular one of the electronic image files being determined based at least in part on the guidelines; receive from a user computing device, a verification of the particular one of the electronic image files; and display the verified particular one of the electronic image files with the payment instrument on the user computing device.
 17. The system of claim 16, the instructions further comprising identifying a status of the payment instrument account on the payment instrument system.
 18. The system of claim 16, wherein the displaying step is performed at the time of a transaction using the payment instrument on the user computing device or upon request input into the user computing device.
 19. The system of claim 16, the instructions further comprising: displaying one or more options for the particular one of the electronic image files for selection on the user computing device; and receiving, from the user computing device, a selection of the particular one of the electronic image files to be associated with the payment instrument.
 20. The system of claim 16, the instructions further comprising: receiving electronic art input into the user computing device, the submitted electronic art complying with the guidelines; and incorporating the submitted art into the options. 